Add standalone Agentuity Pi plugin package#1453
Merged
Conversation
|
The latest Agentuity deployment details.
|
Contributor
📝 WalkthroughWalkthroughA new ChangesPi AI Gateway Package Extraction
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
📦 Canary Packages Publishedversion: PackagesInstallAdd to your {
"dependencies": {
"@agentuity/pi": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-pi-2.0.15-66e9fa2.tgz",
"@agentuity/email": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-email-2.0.15-66e9fa2.tgz",
"@agentuity/evals": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-evals-2.0.15-66e9fa2.tgz",
"@agentuity/webhook": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-webhook-2.0.15-66e9fa2.tgz",
"@agentuity/cli": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-cli-2.0.15-66e9fa2.tgz",
"@agentuity/drizzle": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-drizzle-2.0.15-66e9fa2.tgz",
"@agentuity/postgres": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-postgres-2.0.15-66e9fa2.tgz",
"@agentuity/coder": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-coder-2.0.15-66e9fa2.tgz",
"@agentuity/aigateway": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-aigateway-2.0.15-66e9fa2.tgz",
"@agentuity/sandbox": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-sandbox-2.0.15-66e9fa2.tgz",
"@agentuity/keyvalue": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-keyvalue-2.0.15-66e9fa2.tgz",
"@agentuity/task": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-task-2.0.15-66e9fa2.tgz",
"@agentuity/server": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-server-2.0.15-66e9fa2.tgz",
"@agentuity/react": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-react-2.0.15-66e9fa2.tgz",
"@agentuity/migrate": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-migrate-2.0.15-66e9fa2.tgz",
"@agentuity/workbench": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-workbench-2.0.15-66e9fa2.tgz",
"@agentuity/runtime": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-runtime-2.0.15-66e9fa2.tgz",
"@agentuity/claude-code": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-claude-code-2.0.15-66e9fa2.tgz",
"@agentuity/queue": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-queue-2.0.15-66e9fa2.tgz",
"@agentuity/frontend": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-frontend-2.0.15-66e9fa2.tgz",
"@agentuity/schema": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-schema-2.0.15-66e9fa2.tgz",
"@agentuity/opencode": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-opencode-2.0.15-66e9fa2.tgz",
"@agentuity/schedule": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-schedule-2.0.15-66e9fa2.tgz",
"@agentuity/auth": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-auth-2.0.15-66e9fa2.tgz",
"@agentuity/core": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-core-2.0.15-66e9fa2.tgz",
"@agentuity/coder-tui": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-coder-tui-2.0.15-66e9fa2.tgz",
"@agentuity/vector": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-vector-2.0.15-66e9fa2.tgz",
"@agentuity/db": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-db-2.0.15-66e9fa2.tgz"
}
}Or install directly: bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-pi-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-email-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-evals-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-webhook-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-cli-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-drizzle-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-postgres-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-coder-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-aigateway-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-sandbox-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-keyvalue-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-task-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-server-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-react-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-migrate-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-workbench-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-runtime-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-claude-code-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-queue-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-frontend-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-schema-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-opencode-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-schedule-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-auth-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-core-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-coder-tui-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-vector-2.0.15-66e9fa2.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/2.0.15-66e9fa2/agentuity-db-2.0.15-66e9fa2.tgz |
jhaynie
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/pi/src/index.ts`:
- Line 162: Add a reasonable timeout option to every execFileSync invocation in
packages/pi/src/index.ts (the calls invoking agentuity: the one calling
execFileSync(agentuity, ['auth', 'whoami', '--json']) and the other three
execFileSync calls referenced around lines 179, 220, 225) so the thread can't
block indefinitely; update each call to pass an options object with a timeout
(e.g., 30_000 ms or whatever is appropriate for your CLI) and leave existing
try/catch handling as-is because execFileSync will throw ETIMEDOUT on timeout
and those catches will handle it.
- Around line 211-213: fetchModels currently builds orgId using
normalizeCredential(getEnv('AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID',
'AGENTUITY_ORG_ID')) but getCurrentOrgId checks AGENTUITY_AIGATEWAY_ORGID first,
causing inconsistent behavior; update the orgId resolution inside fetchModels to
include 'AGENTUITY_AIGATEWAY_ORGID' (the same precedence used in
getCurrentOrgId) by adding that key to the getEnv call used with
normalizeCredential so fetchModels will pick up the gateway org id when present.
- Around line 224-229: The code path where execFileSync(fn, ['auth', 'org',
'current']) yields an empty result currently does a silent early return (return
{}) — update the orgId-empty branch in the function that calls execFileSync and
normalizeCredential so it logs a warning (e.g., console.warn or the module's
logger) explaining that the CLI org lookup returned no org and models will not
be loaded, then return {}; ensure you match the style/message used by the other
early-return branches (the ones around the checks at lines 239–242 and 247–248)
and reference orgId, execFileSync, and normalizeCredential when locating the
block to change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 09a6c57a-0713-4b5e-97b5-4651ca2f83b2
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (10)
README.mdpackage.jsonpackages/coder-tui/package.jsonpackages/coder-tui/src/index.tspackages/coder-tui/tsconfig.jsonpackages/pi/README.mdpackages/pi/package.jsonpackages/pi/src/index.tspackages/pi/tsconfig.jsontsconfig.json
✅ Files skipped from review due to trivial changes (5)
- README.md
- packages/pi/README.md
- tsconfig.json
- packages/pi/package.json
- packages/coder-tui/src/index.ts
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/coder-tui/tsconfig.json
- package.json
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)
- GitHub Check: Framework Integration Tests (TanStack & Next.js)
- GitHub Check: Template Integration Tests
- GitHub Check: Queue CLI Tests
- GitHub Check: Playwright E2E Smoke Test
- GitHub Check: Postgres SSL Integration Test
- GitHub Check: SDK Integration Test Suite
- GitHub Check: Cloud Deployment Tests
- GitHub Check: Package Installation & Usage Test
- GitHub Check: Standalone Agent Test
- GitHub Check: Build
- GitHub Check: Pack & Upload
- GitHub Check: Agentuity Deployment
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (AGENTS.md)
Use Biome as code formatter with tabs (width 3), single quotes, semicolons, lineWidth 100, and trailingCommas es5
Files:
packages/pi/src/index.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
**/*.{ts,tsx}: Use TypeScript Strict mode with ESNext target and bundler moduleResolution
UseStructuredErrorfrom@agentuity/corefor error handling
Files:
packages/pi/src/index.ts
**/index.ts
📄 CodeRabbit inference engine (AGENTS.md)
Use named exports from package
index.tsfiles
Files:
packages/pi/src/index.ts
🧠 Learnings (3)
📚 Learning: 2026-01-09T20:33:30.464Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 515
File: apps/testing/nextjs-app/agentuity/tsconfig.json:0-0
Timestamp: 2026-01-09T20:33:30.464Z
Learning: In TypeScript tsconfig.json files used by Agentuity projects, when a generated type file (e.g. .agentuity/.agentuity_types.ts) must be included while its parent directory is excluded, use include with an explicit file path (or a precise glob) instead of files. The files array requires files to exist at parse time and will fail for generated files; include with a suitable pattern allows the file to be picked up once generated without failing if it doesn't exist yet.
Applied to files:
packages/pi/tsconfig.json
📚 Learning: 2026-03-27T23:18:58.450Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 1292
File: packages/keyvalue/package.json:3-3
Timestamp: 2026-03-27T23:18:58.450Z
Learning: In the agentuity/sdk monorepo, subpackage `package.json` files under `packages/` (e.g., `packages/keyvalue`) are allowed to depend on other workspace packages (such as `agentuity/server`) and are not limited to only `agentuity/core` and `zod`. Also, if a subpackage uses `bunx tsc --build --force` as its build script, treat it as a valid/intentional build command and do not flag it as a dependency/build-script violation.
Applied to files:
packages/coder-tui/package.json
📚 Learning: 2025-12-21T00:31:41.858Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 274
File: packages/cli/src/cmd/build/vite/server-bundler.ts:12-41
Timestamp: 2025-12-21T00:31:41.858Z
Learning: In Bun runtime, BuildMessage and ResolveMessage are global types and are not exported from the bun module. Do not import { BuildMessage } from 'bun' or similar; these types are available globally and should be used without import. This applies to all TypeScript files that target the Bun runtime within the repository.
Applied to files:
packages/pi/src/index.ts
🔇 Additional comments (2)
packages/coder-tui/package.json (1)
28-28: Looks good — no blocking concerns in this dependency update.Line 28 is consistent with the package extraction in this PR and valid workspace dependency usage.
Based on learnings: subpackages under
packages/are allowed to depend on other workspace packages.packages/pi/tsconfig.json (1)
9-9: ⚡ Quick winPath mapping is correct.
The wildcard alias
"@agentuity/core/*": ["../core/src/services/*"]correctly maps sub-path imports from the pi package. Verification confirms thataigatewayis located atcore/src/services/aigateway/, and the only sub-path import in pi (@agentuity/core/aigateway) resolves correctly through this mapping. Root-level exports in core are accessible via the non-wildcard mapping.
| return []; | ||
| } | ||
|
|
||
| const res = execFileSync(agentuity, ['auth', 'whoami', '--json']); |
Contributor
There was a problem hiding this comment.
execFileSync calls have no timeout — thread can block indefinitely
All four execFileSync invocations (lines 162, 179, 220, 225) omit the timeout option. If the Agentuity CLI stalls (network auth, slow disk, etc.) the calling thread will block forever, hanging the UI command handler or the entire startup flow.
🛡️ Proposed fix — add a timeout to every `execFileSync` call
- const res = execFileSync(agentuity, ['auth', 'whoami', '--json']);
+ const res = execFileSync(agentuity, ['auth', 'whoami', '--json'], { timeout: 10_000 });- const res = execFileSync(agentuity, ['cloud', 'region', 'list', '--json']);
+ const res = execFileSync(agentuity, ['cloud', 'region', 'list', '--json'], { timeout: 10_000 });- const res = execFileSync(fn, ['auth', 'apikey', '--json']);
+ const res = execFileSync(fn, ['auth', 'apikey', '--json'], { timeout: 10_000 });- const ores = execFileSync(fn, ['auth', 'org', 'current']);
+ const ores = execFileSync(fn, ['auth', 'org', 'current'], { timeout: 10_000 });Note: when the timeout elapses, execFileSync throws an Error with code: 'ETIMEDOUT', so existing catch blocks at each call site already handle it correctly.
Also applies to: 179-179, 220-220, 225-225
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/pi/src/index.ts` at line 162, Add a reasonable timeout option to
every execFileSync invocation in packages/pi/src/index.ts (the calls invoking
agentuity: the one calling execFileSync(agentuity, ['auth', 'whoami', '--json'])
and the other three execFileSync calls referenced around lines 179, 220, 225) so
the thread can't block indefinitely; update each call to pass an options object
with a timeout (e.g., 30_000 ms or whatever is appropriate for your CLI) and
leave existing try/catch handling as-is because execFileSync will throw
ETIMEDOUT on timeout and those catches will handle it.
Comment on lines
+211
to
+213
| let orgId = normalizeCredential( | ||
| getEnv('AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID') | ||
| ); |
Contributor
There was a problem hiding this comment.
fetchModels omits AGENTUITY_AIGATEWAY_ORGID from its initial orgId lookup, inconsistent with getCurrentOrgId
getCurrentOrgId (line 193) checks AGENTUITY_AIGATEWAY_ORGID first, but the orgId resolution inside fetchModels only checks AGENTUITY_ORGID, AGENTUITY_CLOUD_ORG_ID, AGENTUITY_ORG_ID. If a user's environment has only AGENTUITY_AIGATEWAY_ORGID set (or it was written by a previous process invocation), fetchModels silently falls through to CLI-based org lookup instead of using the already-known value.
🐛 Proposed fix
let orgId = normalizeCredential(
- getEnv('AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID')
+ getEnv('AGENTUITY_AIGATEWAY_ORGID', 'AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID')
);📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| let orgId = normalizeCredential( | |
| getEnv('AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID') | |
| ); | |
| let orgId = normalizeCredential( | |
| getEnv('AGENTUITY_AIGATEWAY_ORGID', 'AGENTUITY_ORGID', 'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID') | |
| ); |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/pi/src/index.ts` around lines 211 - 213, fetchModels currently
builds orgId using normalizeCredential(getEnv('AGENTUITY_ORGID',
'AGENTUITY_CLOUD_ORG_ID', 'AGENTUITY_ORG_ID')) but getCurrentOrgId checks
AGENTUITY_AIGATEWAY_ORGID first, causing inconsistent behavior; update the orgId
resolution inside fetchModels to include 'AGENTUITY_AIGATEWAY_ORGID' (the same
precedence used in getCurrentOrgId) by adding that key to the getEnv call used
with normalizeCredential so fetchModels will pick up the gateway org id when
present.
Comment on lines
+224
to
+229
| if (!orgId) { | ||
| const ores = execFileSync(fn, ['auth', 'org', 'current']); | ||
| orgId = normalizeCredential(ores); | ||
| if (!orgId) { | ||
| return {}; | ||
| } |
Contributor
There was a problem hiding this comment.
Silent return {} when CLI org lookup yields an empty result
When the API key is successfully retrieved via the CLI but execFileSync(fn, ['auth', 'org', 'current']) returns an empty string, the function returns {} without any console.warn. The user will see no models loaded and receive no indication of why, unlike the other early-return paths (lines 239–242 and 247–248) which both emit a warning.
🐛 Proposed fix
if (!orgId) {
+ console.warn(
+ 'Could not determine current Agentuity organization; cannot fetch models from AI Gateway'
+ );
return {};
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| if (!orgId) { | |
| const ores = execFileSync(fn, ['auth', 'org', 'current']); | |
| orgId = normalizeCredential(ores); | |
| if (!orgId) { | |
| return {}; | |
| } | |
| if (!orgId) { | |
| const ores = execFileSync(fn, ['auth', 'org', 'current']); | |
| orgId = normalizeCredential(ores); | |
| if (!orgId) { | |
| console.warn( | |
| 'Could not determine current Agentuity organization; cannot fetch models from AI Gateway' | |
| ); | |
| return {}; | |
| } |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/pi/src/index.ts` around lines 224 - 229, The code path where
execFileSync(fn, ['auth', 'org', 'current']) yields an empty result currently
does a silent early return (return {}) — update the orgId-empty branch in the
function that calls execFileSync and normalizeCredential so it logs a warning
(e.g., console.warn or the module's logger) explaining that the CLI org lookup
returned no org and models will not be loaded, then return {}; ensure you match
the style/message used by the other early-return branches (the ones around the
checks at lines 239–242 and 247–248) and reference orgId, execFileSync, and
normalizeCredential when locating the block to change.
Huijiro
added a commit
that referenced
this pull request
May 7, 2026
Brings in the AI Gateway SDK + CLI commands and the standalone Pi plugin (PRs #1451 and #1453 from main), aligning them with v3 conventions: - @agentuity/aigateway client (uses @agentuity/adapter, not /server) - @agentuity/pi plugin (depends on aigateway + adapter, hooked into coder-tui) - agentuity cloud aigateway models|complete CLI commands, ported to Node-compatible APIs (node:fs, node:sqlite shim, readStdinText) - AI Gateway URL added to getServiceUrls() in core + server - @agentuity/core/aigateway subpath export - Docs: AI Gateway API reference page + nav entries - Coder workspace create gains --dependency / --setup-script / --system-prompt support (with shared common.ts helpers) - Coder skill create custom subcommand Also fixes two pre-existing test isolation bugs surfaced by the new suites: - packages/test-utils mockFetch() now auto-restores via onTestFinished, plus a restoreFetch() helper. The previous implementation leaked the mock across files. - packages/opencode sqlite test no longer uses file:NAME?mode=memory&cache=shared URIs (bun:sqlite ignores URI flags by default and was creating literal on-disk files in the repo root). Switched to real temp-file paths with cleanup. Skipped from main: apps/ tree, templates/, and the v2-era dev/index.ts gravity rewrite. Versions bumped to 3.0.0-beta.2 to match the v3 release line.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@agentuity/piworkspace package for Agentuity plugins for the Pi coding agentsetupAIGateway@agentuity/coder-tuito depend on and import@agentuity/piVerification
bunx biome check --write package.json packages/pi packages/coder-tui/src/index.ts packages/coder-tui/package.json packages/coder-tui/tsconfig.json tsconfig.jsonbun run --filter='./packages/pi' buildbun run --filter='./packages/pi' typecheckbun run --filter='./packages/coder-tui' buildbun run --filter='./packages/coder-tui' typecheckbunx tsc --buildSummary by CodeRabbit
Release Notes
New Features
Chores